Skip to main content

This is a new service – your feedback will help us to improve it.

London Borough of Lewisham

Article 4 direction area

There is a problem

  • 78 issue of type invalid category value

Forest Hill Article 4 Direction

reference
A4FH
name
Forest Hill Article 4 Direction
article-4-direction
permitted-development-rights

undefined

Part 1 Class C, Part 2 Class C, Part 1 Class A Part 1, Class D, Part 1 Class E, Part 1 Class F, Part 2 Class A
uprns
address-texts
geometry
MULTIPOLYGON (((-0.063869 51.442095,-0.063584 51.442469,-0.063419 51.442740,-0.063438 51.442743,-0.063369 51.442857,-0.063348 51.442855,-0.063276 51.442973,-0.063247 51.443068,-0.063321 51.443074,-0.062890 51.444046,-0.062835 51.444155,-0.062571 51.444855,-0.062450 51.445144,-0.062334 51.445406,-0.062228 51.445587,-0.062189 51.445677,-0.062084 51.445830,-0.061992 51.445985,-0.061859 51.446288,-0.061517 51.446838,-0.061334 51.447079,-0.060452 51.447981,-0.060288 51.448118,-0.060785 51.448491,-0.061500 51.448032,-0.061807 51.447794,-0.062019 51.447573,-0.062242 51.447297,-0.062745 51.446621,-0.062949 51.446311,-0.063213 51.445809,-0.063353 51.445476,-0.063493 51.445100,-0.063612 51.444756,-0.063679 51.444489,-0.063700 51.444206,-0.063654 51.443751,-0.063647 51.443417,-0.063699 51.442959,-0.063763 51.442721,-0.064019 51.442113,-0.063869 51.442095)))
point
POINT (-0.062458 51.445785)
notes
entry-date
2026-02-25
start-date
end-date

How to fix this issue

Your data is missing a permitted-development-rights.

The Article 4 direction area guidance explains how to fix the issue:

permitted-development-rights

A list of the permitted development rights withdrawn by the article 4 direction.

Separate the rights in the list using semicolons.

Only use rights from our permitted development right dataset. If the area withdraws a permitted development right that is not in our dataset, email digitalland@communities.gov.uk.

Example: 3D;3M;11B

How to improve London Borough of Lewisham’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL